Oracle Database
This chapter describes how to add monitoring for a standalone SAP Oracle database from a central monitoring installation. For more information about the central monitoring system, see the chapter Installing CrystalBridge® Monitoring.
Technical Prerequisites
The monitoring system requires software to allow connections to the Oracle database especially in heterogeneous landscapes. Specifically, the following requirements apply:
-
SAP kernel DBSL for the Oracle database
-
Oracle client software on application servers, e.g. SAP Note 819829
-
Depending on the setup changes, application server restarts can be necessary
Prerequisites for External Oracle Database Monitoring
The following prerequisites exist for external Oracle database monitoring:
-
The server defined in CrystalBridge® Monitoring has been connected to the Oracle database.
-
A valid connect user has been created within the monitored Oracle database. For security and password management reasons, we recommend creating a new specific monitoring user, e.g. CBMON-<system ID of the central monitoring system>. For more information about connect users, see the chapter Prerequisites for the Oracle Connect User.
-
A valid database connection has been defined in the table DBCON on the monitored SAP system according to the steps described in the chapter Creating a Secondary Connection to an Oracle Database.
-
A connection test for the database connection can be performed by executing the report ADBC_TEST_CONNECTION or directly via transaction DBACOCKPIT.
-
If the Oracle database is monitored through a remote SAP system via RFC destination, a valid database connection must be defined in the table DBCON on the monitored remote SAP system.
-